Hey @debsmita1, nice work on the i18n coverage and tests!

Two concerns about the updateWidgetComponentData approach:

1. Coupling to Backstage internals — We're directly mutating __backstage_data, an undocumented internal of @backstage/core-plugin-api. If upstream renames/restructures this, our translations silently break with zero errors.

2. Magic string sync — widgetTranslationKeysByName maps names like 'Red Hat Developer Hub - Onboarding' to translation keys. These must stay manually in sync with params.name in homePageCards.tsx. A rename = silent i18n breakage.

Upstream proposal: The root cause is HomePageWidgetBlueprint only accepts plain string for title. Could we push upstream for a titleKey/descriptionKey field, where the renderer just calls t(titleKey) at render time? No internals mutation needed:

// Proposed upstream API
HomePageWidgetBlueprint.make({
  params: {
    titleKey: 'recentlyVisited.title',
    descriptionKey: 'recentlyVisited.description',
  }
})